<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
  <head>
    <meta name="author" content="Paul Bender, Piotr Oniszczuk" />
    <meta name="copyright" content="2006-2014 Paul Bender &amp; Minimyth2.homenet.org" />
    <meta name="keywords" content="MiniMyth2,Linux,PVR,Linux,MythTV,diskless,Mini-ITX,EPIA" />
    <meta name="description" content="" />
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>MiniMyth2 - Documents - Configuration Instructions</title>
    <style type="text/css" title="main-styles">
      @import "/css/minimyth.css";
    </style>
  </head>
  <body>
    <div class="main">
      <div class="header">
        <div class="heading">MiniMyth2</div>
        <div class="menu">
          <span class="menuItemFirst"><a href="index.html">Home</a></span>
          <span class="menuItem"     ><a href="document.html">Documents</a></span>
          <span class="menuItem"     >Configure</span>
        </div>
      </div>
      <div class="middle">
        <div class="heading">Configuration Instructions</div>
        <div id="toc" class="section">
          <div class="heading">Table of contents</div>
          <dl>
            <dt><a href="#general">General</a></dt>
            <dt><a href="#bootline">Configuration obtained from the boot line</a></dt>
            <dt><a href="#dhcp">Configuration obtained from the DHCP server</a></dt>
            <dt><a href="#location">Location of configuration files</a></dt>
            <dt><a href="#minimyth_conf">Configuration obtained from the MiniMyth2 configuration file</a></dt>
            <dt><a href="#minimyth_script">Configuration obtained from the MiniMyth2 configuration script (sh init)</a></dt>
            <dt><a href="#misc">Configuration obtained from miscellaneous configuration files</a></dt>
          </dl>
        </div>
        <div id="general" class="section">
          <div class="heading">General</div>
          <p>
            MiniMyth2 obtains configuration from the following places:
          </p>
          <ul>
            <li><a href="#bootline">the boot line</a>,</li>
            <li><a href="#dhcp">the DHCP server</a>,</li>
            <li><a href="#minimyth_conf">the MiniMyth2 configuration file</a>,</li>
            <li><a href="#minimyth_script">the MiniMyth2 configuration script (sh init)</a> or</li>
            <li><a href="#misc">miscellaneous configuration files</a>.</li>
          </ul>
          <p>
            Ideally, the MiniMyth2 configuration script and the miscellaneous configuration files should not be needed.
            However, MiniMyth2 still lacks configuration files for many remote control recievers, remote controls, and LCD and VFD displays.
            In addition, MiniMyth2 still lacks the flexibility needed for some X Window System configurations.
            If you have configuration files for your hardware and setup that you would like included in MiniMyth2, then
            <a href="http://MiniMyth2.freeforums.org">let us know</a>
            and provide a list of you hardware including vendor and model,
            the outputs of the commands 'lspci&nbsp;-mn' and 'lsusb' with all you hardware connected,
            and the configuration files you want included.
          </p>
        </div>
        <div id="bootline" class="section">
          <div class="heading">Configuration obtained from the boot line</div>
          <p>
            MiniMyth2 can obtain configuration from the
            <a href="document-boot.html#bootline">boot line</a>.
            The following boot line parameters are of some interest:
          </p>
          <ul>
            <li>
              Linux parameters:
              <dl>
                <dt id="debug"><strong>debug</strong></dt>
                <dd>
                  <p>
                    Enables kernel debug logging and disables the boot splash screen.
                  </p>
                </dd>
                <dt id="irqpoll"><strong>irqpoll</strong></dt>
                <dd>
                  <p>
                    Works around IRQ problems with the ASUS A8N-VM CSM motherboard
                    that can cause a a kernel oops when the nvidia kernel driver is loaded,
                    resulting in X not starting correctly.
                  </p>
                </dd>
              </dl>
            </li>
            <li>
              MiniMyth2 variables:
              <dl>
                <dt id="MM_DEBUG"><strong>MM_DEBUG</strong></dt>
                <dd>
                  <p>
                    Enables MiniMyth2 debug logging.
                    Valid values are "yes" and "no", with "no" being the default.
                  </p>
                </dd>
              </dl>
              <p>
                In addition to
                <a href="MM_DEBUG">MM_DEBUG</a>
                you can include any variables found in the
                <a href="document-minimyth_conf.html">MiniMyth2 Configuration File</a>
                on the boot line.
                However, with the exception of some of the
                <a href="document-minimyth_conf.html#MM_DHCP">DHCP override variables</a>,
                there is little reason to include these variables on the boot line.
              </p>
              <p>
                Unlike in the MiniMyth2 configuration file where MiniMyth2 variable values should be single quoted ('),
                MiniMyth2 variable values on the boot line must either be unquoted or double quoted (").
              </p>
            </li>
          </ul>
        </div>
        <div id="dhcp" class="section">
          <div class="heading">Configuration obtained from the DHCP server</div>
          <p>
            MiniMyth2 obtains some configuration from the DHCP server.
          </p>
          <dl>
            <dt id="dhcp-host-name"><strong>Host Name</strong></dt>
            <dd>
              <p>
                The MiniMyth2 frontend's
                <a href="http://en.wikipedia.org/wiki/Hostname">host name</a>.
                MiniMyth2 requires a host name for storing/retrieving the MythTV frontend settings in/from the MythTV's database.
                Therefore, if MiniMyth2 does not obtain a host name,
                then MiniMyth2 will abort its boot process and output an error.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 12 (0x0c), which is supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should enable the 'use-host-decl-names' option and set the 'host' and 'hardware' options in your dhcpd.conf file
              </p>
              <p>
                In addition to using the host name when making MythTV database accesses,
                MiniMyth2 can use the host name when retrieving host specific configuration files.
              </p>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_HOST_NAME">MM_DHCP_HOST_NAME</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
              </p>
            </dd>
            <dt id="dhcp-domain-name"><strong>Domain Name</strong></dt>
            <dd>
              <p>
                The MiniMyth2 frontend's
                <a href="http://en.wikipedia.org/wiki/Domain_name">domain name</a>.
                MiniMyth2 does not require a domain name,
                but it can be useful when using DNS to resolve local network hostnames to IPv4 addresses.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 15 (0x0f), which is supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should set the 'domain-name' option in your dhcpd.conf file.
              </p>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_DOMAIN_NAME">MM_DHCP_DOMAIN_NAME</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
              </p>
            </dd>
            <dt id="dhcp-domain-name-servers"><strong>Domain Name Servers</strong></dt>
            <dd>
              <p>
                A space separated list of
                <a href="http://en.wikipedia.org/wiki/Domain_name_system">Domain Name System (DNS)</a>
                server IPv4 addresses that the MiniMyth2 frontend will use to resolve DNS names.
                MiniMyth2 needs a DNS server to resolve Internet host name to Internet Protocol addresses.
                Therefore, if MiniMyth2 does not obtain a DNS server address,
                then MiniMyth2 will abort its boot process and output an error message.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 6 (0x06), which is supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should set the 'domain-name-servers' option in your dhcpd.conf file.
              </p>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_DOMAIN_NAME_SERVERS">MM_DHCP_DOMAIN_NAME_SERVERS</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
              </p>
            </dd>
            <dt id="dhcp-ntp-servers"><strong>NTP Servers</strong></dt>
            <dd>
              <p>
                A space separated list of
                <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">Network Time Protocol (NTP)</a>
                server IPv4 addresses that the MiniMyth2 frontend will use to synchronize its clock.
                MiniMyth2's clock needs to be synchronized to the MythTV backend's clock or
                fastforward, rewind and commercial skip will fail.
                Therefore, if MiniMyth2 does not obtain an NTP server address,
                then MiniMyth2 will abort its boot process and output an error message.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 42 (0x2a), which is supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should set the 'ntp-servers' option in your dhcpd.conf file.
              </p>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_NTP_SERVERS">MM_DHCP_NTP_SERVERS</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
                If you specify
                <a href="document-minimyth_conf.html#MM_DHCP_NTP_SERVERS">MM_DHCP_NTP_SERVERS</a>
                in your
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                and if either your DHCP server returns a valid list of Domain Name Servers
                or you specify
                <a href="document-minimyth_conf.html#MM_DHCP_DOMAIN_NAME_SERVERS">MM_DHCP_DOMAIN_NAME_SERVERS</a>
                on the
                <a href="#bootline">boot line</a>,
                then
                <a href="document-minimyth_conf.html#MM_DHCP_NTP_SERVERS">MM_DHCP_NTP_SERVERS</a>
                may contain either IPv4 addresses or fully qualified domain names.
              </p>
            </dd>
            <dt id="dhcp-log-servers"><strong>Log Servers</strong></dt>
            <dd>
              <p>
                A list of
                <a href="http://en.wikipedia.org/wiki/Syslog">syslog</a>
                server IPv4 addresses to which MiniMyth2 will log.
                MiniMyth2 will log to the first log server in the list.
                If MiniMyth2 does not obtain a log server address,
                then MiniMyth2 will log locally.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 7 (0x07), which is supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should set the 'log-servers' option in your dhcpd.conf file.
              </p>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_LOG_SERVERS">MM_DHCP_LOG_SERVERS</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
                If you specify
                <a href="document-minimyth_conf.html#MM_DHCP_LOG_SERVERS">MM_DHCP_LOG_SERVERS</a>
                in your
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                and if either your DHCP server returns a valid list of Domain Name Servers
                or you specify
                <a href="document-minimyth_conf.html#MM_DHCP_DOMAIN_NAME_SERVERS">MM_DHCP_DOMAIN_NAME_SERVERS</a>
                on the
                <a href="#bootline">boot line</a>,
                then
                <a href="document-minimyth_conf.html#MM_DHCP_LOG_SERVERS">MM_DHCP_LOG_SERVERS</a>
                may contain either IPv4 addresses or fully qualified domain names.
              </p>
            </dd>
            <dt id="dhcp-tcode"><strong>TCode</strong></dt>
            <dd>
              <p>
                The tz database
                (a.k.a. the <a href="http://en.wikipedia.org/wiki/Zoneinfo">zoneinfo</a> database)
                name of your MiniMyth2 frontend's
                <a href="http://en.wikipedia.org/wiki/Time_zone">time zone</a>.
                MiniMyth2's time zone needs to be correct or fastforward, rewind and commercial skip will fail.
                Therefore, if MiniMyth2 does not obtain time zone,
                then MiniMyth2 will abort its boot process and output an error message.
              </p>
              <p>
                The
                <a href="http://www.iana.org/assignments/bootp-dhcp-parameters">DHCP option</a>
                is 101 (0x65), which is not supported by
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>.
                Therefore, if your DHCP server is
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you should define and set the 'tcode' option in your dhcpd.conf file.
              </p>
              <p>
                As mentioned above,
                if you want to use the 'tcode' option in
                <a href="http://www.isc.org/index.pl?/sw/dhcp/">ISC DHCP</a>,
                then you will need to define it in your dhcpd.conf file.
                As defined in
                <a href="http://www.rfc-editor.org/rfc/rfc4833.txt">RFC 4833</a>,
                the 'tcode' option is a string identified by the tag 101 (0x65).
                As explained in the
                <a href="http://www.linuxmanpages.com/man5/dhcp-options.5.php">dhcp-options</a>
                man page,
                this new option is defined by adding the following line to
                <a href="http://www.linuxmanpages.com/man5/dhcpd.conf.5.php">dhcpd.conf</a>:
              </p>
<pre>option tcode code 101 = text;</pre>
              <p>
                After that, you can use 'tcode' as you would any other option,
                with the option value being the tz database name for your time zone.
                For example:
              </p>
<pre>option tcode "America/Los_Angeles";</pre>
              <p>
                If you DHCP server does not support this option, then you can use the
                <a href="document-minimyth_conf.html#MM_DHCP_TCODE">MM_DHCP_TCODE</a>
                DHCP override variable either on the
                <a href="#bootline">boot line</a>
                or in the
                <a href="#minimyth_conf">MiniMyth2 configuration file</a>
                instead.
              </p>
            </dd>
          </dl>
        </div>
        <div id="location" class="section">
          <div class="heading">Location of configuration files</div>
          <p>
            MiniMyth2 looks for configuration files and scripts in the MiniMyth2 configuration directories.
            There are two MiniMyth2 configuration directories:
            the read-only configuration directory and the read-write configuration directory.
          </p>
          <p>
            The MiniMyth2 read-only configuration directory is named 'conf' and is required.
            This directory (actually a sub-directory of this directory) is where you would put configuration files that you create.
            This directory may be read-only.
          </p>
          <p>
            The MiniMyth2 read-write configuration directory is named 'conf-rw' and is optional.
            This directory is where MiniMyth2 put files that it creates.
            For example, when MiniMyth2 saves game configurations it saves them in this directory.
            This directory is only required when you are using a MiniMyth2 feature that saves files across reboot.
            This directory must be read-write.
            In addition, if this directory is on a TFTP server,
            then you need to be sure that the TFTP server is configured to allow file creation not just file upload.
          </p>
          <p>
            MiniMyth2 looks for the MiniMyth2 configuration directories in the MiniMyth2 boot directory.
            If neither the
            <a href="#bootline">boot line</a>
            nor the
            <a href="#minimyth_conf">MiniMyth2 configuration file</a>
            provide
            '<a href="document-minimyth_conf.html#MM_MINIMYTH_BOOT_URL">MM_MINIMYTH_BOOT_URL</a>',
            then MiniMyth2 'guesses' the location of the boot directory as follows.
            If MiniMyth2 'guesses' that
            <a href="document-boot.html#network">network boot</a>
            was used, then MiniMyth2 assumes that the boot directory is the directory on the TFTP server that contains the boot loader
            (i.e. url="tftp://${MM_TFTP_SERVER}${MM_TFTP_ROOTDIR)/").
            If MiniMyth2 is not able to download configuration file from read-only configuration directory - MiniMyth2 will look
            for minimyth.conf on local partition with label 'BOOTFS'. If minimyth.conf will be found - MiniMyth2 will use this file
            as setings file. If no minimyth.conf file will be found - MiniMyth2 will use build-in default settings.
          </p>
          <p>
            In practice, this means that
            if you network boot MiniMyth2
            then you put the MiniMyth2 configuration directories in the same directory on the TFTP server as the network boot loader
            (called 'pxelinux.0' when using PXELinux).
            If you boot MiniMyth2 from SD card, then you put the MiniMyth2 configuration file at the root of the partition labeled 'BOOTFS',
            which MiniMyth2 will automatically mount and read config file.
          </p>
          <p>
            Once MiniMyth2 has determined the boot directory (lets call it '{boot}'),
            then MiniMyth2 looks for read-only configuration files
            first as the file '{boot}/conf/{hostname}/{file}' and
            second as the file '{boot}/conf/default/{file}',
            and looks for read-write configuration files
            as the file '{boot}/conf-rw/{hostname}+{file}',
            where '{hostname}' is the hostname of the MiniMyth2 frontend
            and '{file}' is the name of the configuration file.
          </p>
        </div>
        <div id="minimyth_conf" class="section">
          <div class="heading">Configuration obtained from the MiniMyth2 configuration file</div>
          <p>
            The MiniMyth2 configuration file is called 'minimyth.conf'.
            The MiniMyth2 configuration file is required.
            You can find information on the configuration that can be obtained from MiniMyth2 configuration file in the
            <a href="document-minimyth_conf.html">minimyth.conf description</a>.
          </p>
        </div>
        <div id="minimyth_script" class="section">
          <div class="heading">Configuration obtained from the MiniMyth2 configuration script (sh init)</div>
          <p>
            The MiniMyth2 configuration script.
            The MiniMyth2 configuration script is called 'MiniMyth2.script'.
            The MiniMyth2 configuration script is optional.
            The MiniMyth2 configuration script is a shell script that is executed by MiniMyth2
            after MiniMyth2 has retrieved and imported (but not processed) the MiniMyth2 configuration file and
            updated DHCP configuration.
            You can use the MiniMyth2 configuration script to do things such as change the startup or shutdown scripts.
            Whether or not 'minimyth.script' is retrieved depends on
            '<a href="document-minimyth_conf.html#MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT">MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT</a>'.
          </p>
          <p>
            As mentioned above 'minimyth.script' is a shell script.
            The following is a stub for the shell script:
          </p>
          <pre>
#!/bin/sh

. /etc/rc.d/functions

exit 0;
          </pre>
        </div>
        <div id="misc" class="section">
          <div class="heading">Configuration obtained from miscellaneous configuration files</div>
          <p>
            MiniMyth2 can override the following configuration files:
          </p>
          <dl>
            <dt id="authorized_keys">authorized_keys</dt>
            <dd>
              <p>
                An SSH authorized keys file.
                This file contains the public keys of users that are allowed to connect to the SSH server
                as the user 'root' using public key authentication.
                The format of this file must be in the format of an
                <a href="http://www.openssh.org/">OpenSSH</a>
                authorized keys file.
                Whether or not 'authorized_keys' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_SSH_SERVER_ENABLED">MM_SSH_SERVER_ENABLED</a>'.
              </p>
            </dd>
            <dt id="ca_bundle_crt">ca_bundle.crt</dt>
            <dd>
              <p>
                The bundle digital certificates for trusted certificate authorities.
                Whether or not 'ca-bundle.crt' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_SECURITY_FETCH_CA_BUNDLE_CRT">MM_SECURITY_FETCH_CA_BUNDLE_CRT</a>'.
              </p>
            </dd>
            <dt>crontab</dt>
            <dd>
              <p>
                The crontab file for user root.
                Whether or not 'crontab' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_CRON_FETCH_CRONTAB">MM_CRON_FETCH_CRONTAB</a>'.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="credentials_cifs">credentials_cifs</dt>
            <dd>
              <p>
                A CIFS credentials file for mount.cifs.
                This file contains the username and password that allows MiniMyth2 to mount CIFS network shares.
                The format of this file must be in the format described in
                <a href="http://samba.org/samba/docs/man/manpages-3/mount.cifs.8.html">the mount.cifs man page</a>.
                Whether or not 'credentials_cifs' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_FETCH_SECURITY_CREDENTIALS_CIFS">MM_SSECURITY_FETCH_CREDENTIALS_CIFS</a>'.
              </p>
              <p>
                <em>WARNING:</em>
                Because access to the TFTP server storing this file is not secure,
                <em>the credentials in this file should not be trusted</em>.
                You should assume that because it can be compromised that it will be compromised.
                Therefore, when using network boot,
                do not allow anything identifying itself using these credentials to do anything that could be harmful.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="id_rsa">id_rsa</dt>
            <dd>
              <p>
                <em>WARNING:</em>
                Because access to the TFTP server storing this file is not secure,
                <em>the SSH RSA private key in this file should not be trusted</em>.
                You should assume that because it can be compromised that it will be compromised.
                Therefore, when using network boot,
                do not allow anything identifying itself using this identity file to do anything that could be harmful.
              </p>
            </dd>
            <dt id="LCDd_conf">LCDd.conf</dt>
            <dd>
              <p>
                The LCDproc daemon ('LCDd') configuration file.
                MiniMyth2 will use this file as the '/etc/LCDd.conf' file in the MiniMyth2 file system.
                Whether or not 'LCDd.conf' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_LCDPROC_FETCH_LCDD_CONF">MM_LCDPROC_FETCH_LCDD_CONF</a>'.
              </p>
            </dd>
            <dt id="lircd_conf">lircd.conf</dt>
            <dd>
              <p>
                The LIRC daemon ('lircd') configuration file.
                MiniMyth2 will use this file as the '/etc/lircd.conf' file in the MiniMyth2 file system.
                Whether or not 'lircd.conf' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_LIRC_FETCH_LIRCD_CONF">MM_LIRC_FETCH_LIRCD_CONF</a>'.
              </p>
            </dd>
            <dt id="lircrc">lircrc</dt>
            <dd>
              <p>
                The LIRC configuration file.
                MiniMyth2 will use this file as the '/etc/lircrc' file in the MiniMyth2 file system.
                Whether or not 'lircrc' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_LIRC_FETCH_LIRCRC">MM_LIRC_FETCH_LIRCRC</a>'.
              </p>
            </dd>
            <dt id="microcode_dat">microcode.dat</dt>
            <dd>
              <p>
                The Intel CPU microcode data file.
                MiniMyth2 will use this file as the '/etc/firmware/microcode.dat' file in the MiniMyth2 file system,
                and load the microcode during initialization when '/etc/firmware/microcode.dat' is present.
                Whether or not 'microcode.dat' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_CPU_FETCH_MICROCODE_DAT">MM_CPU_FETCH_MICROCODE_DAT</a>'.
              </p>
              <p>
                You can find out more about the Intel CPU microcode data file at the
                <a href="http://www.urbanmyth.org/microcode/">'microcode_ctl' utility</a>
                page.
              </p>
            </dd>
            <dt id="ssh_host_rsa_key">ssh_host_rsa_key</dt>
            <dd>
              <p>
                An SSH private RSA identity file.
                This file is the host key of the SSH server.
                The format of these files must be in the format of an
                <a href="http://www.openssh.org/">OpenSSH</a>
                private RSA key as generated by
                <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-keygen">ssh-keygen</a>.
                Whether or not 'ssh_host_rsa_key' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_SSH_SERVER_ENABLED">MM_SSH_SERVER_ENABLED</a>'.
              </p>
              <p>
                <em>WARNING:</em>
                Because access to the TFTP server storing this file is not secure,
                <em>the SSH RSA private key in this file should not be trusted</em>.
                You should assume that because it can be compromised that it will be compromised.
                Therefore, when using network boot,
                do not allow anything identifying itself using this identity file to do anything that could be harmful.
              </p>
            </dd>
            <dt id="xinitrc">xinitrc</dt>
            <dd>
              <p>
                The X Window System (Xorg) startup file.
                MiniMyth2 will use this file as the '/etc/X11/xinit/xinitrc' file in the MiniMyth2 file system.
                Whether or not 'xinitrc' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_X_FETCH_XINITRC">MM_X_FETCH_XINITRC</a>'.
              </p>
            </dd>
            <dt id="xmodmaprc">xmodmaprc</dt>
            <dd>
              <p>
                The X Window System (Xorg) startup file.
                The X Window System (Xorg) keyboard map file.
                MiniMyth2 will use this file as the '/etc/X11/xmodmaprc' file in the MiniMyth2 file system.
                Whether or not 'xmodmaprc' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_X_FETCH_XMODMAPRC">MM_X_FETCH_XMODMAPRC</a>'.
              </p>
              <p>
                This file is loaded by MiniMyth2's build-in '/etc/X11/xinit/xinitrc' file using the 'xmodmap' utility.
                Therefore, if you override '/etc/X11/xinit/xinitrc', then you will need to load '/etc/X11/xmodmaprc'.
              </p>
            </dd>
            <dt id="xorg_conf">xorg.conf</dt>
            <dd>
              <p>
                The X Window System (Xorg) configuration file.
                MiniMyth2 will use this file as the '/etc/X11/xorg.conf' file in the MiniMyth2 file system.
                Whether or not 'xorg.conf' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_X_FETCH_XORG_CONF">MM_X_FETCH_XORG_CONF</a>'.
              </p>
            </dd>
            <dt id="sleep_workarounds_script">sleep_workarounds.script</dt>
            <dd>
              <p>
                The Suspend-To-RAM configuration file.
                MiniMyth2 will execute this file as script directly before entering Suspend-to-RAM.
                Whether or not 'sleep_workarounds.script' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_S3_WORKAROUNDS">MM_S3_WORKAROUNDS</a>'.
              </p>
            </dd>
            <dt id="resume_workarounds_script">resume_workarounds.script</dt>
            <dd>
              <p>
                The Suspend-To-RAM configuration file.
                MiniMyth2 will execute this file as script directly after returning from Suspend-to-RAM.
                Whether or not 'resume_workarounds.script' is retrieved depends on
                '<a href="document-minimyth_conf.html#MM_S3_WORKAROUNDS">MM_S3_WORKAROUNDS</a>'.
              </p>
            </dd>
            <dt id="mailnotifier_rc">mailnotifier.rc</dt>
            <dd>
              <p>
                New Mails OSD notification configuration file.
                MiniMyth2 will use this file to access mail accounts for checking new mails.
                Format of this file is following:
                '<a href="document-minimyth_conf.html#MM_MAIL_NOTIFY_NEW_MAILS">MM_MAIL_NOTIFY_NEW_MAILS</a>'.
              </p>
            </dd>
          </dl>
          <p>
            If you want to override any other configuration files,
            then you will need to use the
            <a href="#minimyth_script">MiniMyth2 configuration script (sh init)</a>
          </p>
        </div>
      </div>
      <div class="footer">
        <hr />
        <div class="valid-xhtml">
          <a href="http://validator.w3.org/check?uri=referer"><img
              src="/image/w3c-valid-xhtml11-blue.gif"
              alt="Valid XHTML 1.1" height="31" width="88" /></a>
        </div>
        <div class="valid-css">
          <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
              src="/image/w3c-valid-css2-blue.gif"
              alt="Valid CSS!"      height="31" width="88" /></a>
        </div>
        <div class="version">
          Last Updated on 2017-08-10
          <br />
          &lt;&nbsp;mailto&nbsp;:&nbsp;warpme&nbsp;at&nbsp;o2&nbsp;dot&nbsp;pl&nbsp;&gt;
        </div>
      </div>
    </div>
  </body>
</html>
